Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1216

reference
113-tree-1
name
1216
tree-preservation-order

undefined

113-tpo-1
uprn
address-text
point
POINT (-1.011532 50.866161)
geometry
MULTIPOLYGON (((-1.011476 50.866155,-1.011478 50.866166,-1.011486 50.866176,-1.011498 50.866184,-1.011514 50.866190,-1.011532 50.866191,-1.011549 50.866190,-1.011565 50.866185,-1.011578 50.866177,-1.011586 50.866167,-1.011589 50.866156,-1.011587 50.866145,-1.011579 50.866135,-1.011566 50.866127,-1.011551 50.866121,-1.011533 50.866120,-1.011516 50.866121,-1.011500 50.866126,-1.011487 50.866134,-1.011479 50.866144,-1.011476 50.866155)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL